Encryption key exchange process using access device

ABSTRACT

Encryption key exchange processes are disclosed. A disclosed method includes initiating communication between a portable communication device including a token and a first limited use encryption key, and an access device. After communication is initiated, the portable communication device receives a second limited use key from a remote server via the access device. The portable communication device then replaces the first limited use key with the second limited use key. The second limited use key is thereafter used to create access data such as cryptograms that can be used to conduct access transactions.

CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a National Stage of International Application No. PCT/US2017/041220 filed Jul. 7, 2017, and which claims the benefit of U.S. Patent Application No. 62/360,768 filed Jul. 11, 2016, of which are all herein incorporated by reference.

BACKGROUND

Encryption keys that can be used to generate access data such as cryptograms are typically provisioned to portable communication devices over the air through cellular telephone networks. While such systems are effective, there are many portable communication device form factors that are capable of conducting access transactions, but are not capable of communicating with a remote provisioning server computer to receive such encryption keys. For example, payment cards, wearable devices such as rings and watches, and key fobs are capable of being used to conduct access transactions such as payment transactions as they may contain integrated circuits and short range communication capabilities (e.g., RF ID chips). However, they cannot receive encryption keys directly from a remote provisioning server computer over a cellular network, because they do not have long range communication capabilities. Such devices are typically pre-loaded with any encryption keys that are needed to conduct access transactions at the time of manufacture.

In addition, even if a portable communication device did have remote communication capabilities, there may be instances when the portable communication device may not be able to connect to the remote provisioning server computer. For example, cellular networks can go down or may be susceptible to dead zones (e.g., within a building that cannot receive a cellular signal). In such instances, the portable communication device may not be able to retrieve the encryption keys needed to conduct access transactions. As a result, the user of the portable communication device would be prohibited from conducting the desired transaction.

There is a need to provide for systems and methods that can allow for portable communication devices such as those that cannot receive communications over cellular networks (e.g., either permanently or temporarily) with the ability to receive encryption keys on a regular basis, so that access transactions can be conducted with the portable communication devices in a secure and reliable manner.

Embodiments of the invention address these and other problems, individually and collectively.

BRIEF SUMMARY

Embodiments of the invention can provide portable communication devices with encryption keys that can be used to generate access data such as cryptograms. This can be done even though the portable communication devices do not have long range communication capabilities and/or cannot access a remote provisioning server computer through a long range communication medium.

Some embodiments of the present invention provide techniques for enhancing the security of a communication device (e.g., a portable communication device) when conducting a transaction using the communication device. The techniques described herein can be used with a communication device that does not have a secure element. Embodiments of the invention can instead use limited-use encryption keys that have a limited lifespan. Once expired, they can no longer be used to conduct a transaction until the limited-use encryption keys are replenished. Such replenishment need not rely on long range communication with a remote provisioning server computer. In embodiments of the invention, the replenishment can occur via a short-range wireless communication or contact connection with an access device such as point of sale terminal. As such, portable communication devices such as wearable devices and payment cards may be provided with greater security, even though they may not have secure elements and/or remote, over-the-air communication capabilities.

One embodiment of the invention is directed to a method. The method comprises initiating communication between a portable communication device comprising a token and a first limited use key, and an access device, and then receiving, by the portable communication device, from a remote server via the access device, a second limited use key. The portable communication device is in short range communication or in contact with the access device. The portable communication device then replaces the first limited use key with the second limited use key.

Another embodiment of the invention is directed to a portable communication device comprising a processor, and a computer readable medium. The computer readable medium comprising code, executable by the processor to implement a method comprising: initiating communication between the portable communication device comprising a token and a first limited use key, and an access device; receiving from a remote server via the access device, a second limited use key, wherein the portable communication device is in short range communication or in contact with the access device; and replacing the first limited use key with the second limited use key.

Another embodiment of the invention is directed to a method. The method includes communicating, by an access device, with a portable communication device comprising a token and a first limited use key, and then receiving, by the access device, a second limited use key from a remote server computer. The access device then provides the second limited use key to the portable communication device. The portable communication device is in short range communication or in contact with the access device.

Another embodiment of the invention is directed to an access device comprising a processor, and a computer readable medium. The computer readable medium comprises code, executable by the processor, to implement a method comprising communicating with a portable communication device comprising a token and a first limited use key; receiving a second limited use key from a remote server computer; and providing to the portable communication device, the second limited use key. The portable communication device is in short range communication or in contact with the access device.

According to some embodiments, a method for enhancing the security of a communication device when conducting a transaction using the communication device may include receiving, from an access device, a limited-use key (LUK) that is associated with a set of one or more limited-use thresholds that limits usage of the LUK. The method may also include generating, by the communication device, a cryptogram using the LUK, and sending, by the communication device to an access device, a token instead of a real account identifier and the transaction cryptogram to conduct the transaction. The transaction can be authorized based on at least whether usage of the LUK has exceeded the set of one or more limited-use thresholds.

According to some embodiments, a communication device may include a processor; and a memory coupled to the processor and storing a mobile application that performs operations for enhancing security of the communication device when conducting transactions using the communication device. The operations may include receiving a limited-use key (LUK) that is associated with a set of one or more limited-use thresholds that limits usage of the LUK, generating a transaction cryptogram using the LUK, and sending a token instead of a real account identifier and the transaction cryptogram to conduct the transaction. The transaction may be authorized based on at least whether usage of the LUK has exceeded the set of one or more limited-use thresholds.

These and other embodiments of the invention are described in further detail below.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a block diagram of an example of a system according to some embodiments.

FIG. 2 illustrates a communication flow diagram of an example of executing an integrated chip based transaction, according to some embodiments.

FIG. 3 shows a flow diagram illustrating a method for provisioning a limited use key, according to some embodiments.

FIG. 4 shows a flow diagram illustrating another method for provisioning a limited use key in an authorization processing scheme, according to some embodiments.

FIG. 5 illustrates an example of a transaction verification log, according to some embodiments.

FIG. 6 illustrates an example of a process for generating a transaction cryptogram, according to some embodiments.

FIG. 7 illustrates an example of an encryption function, according to some embodiments.

FIG. 8 shows a block diagram of an access device, according to an embodiment of the invention.

FIG. 9 shows a block diagram of a portable communication device, according to an embodiment of the invention.

DETAILED DESCRIPTION

HCE (host card emulation) based token deployments do not rely on secure hardware to store tokens. In a conventional HCE based token deployment, a limited use encryption key or “LUK” is provisioned to a mobile phone over the air along with a payment token. The LUK may be used by the mobile phone to generate a cryptogram. In a transaction, the cryptogram and the access token are passed from the mobile phone to an access device such a POS terminal. The access device transmits the cryptogram and the access token to a remote server computer, which then validates the cryptogram and continues to processes the access token if the cryptogram is valid.

While conventional methods for delivering LUKs to mobile phones are effective, many other form factors are not capable of communicating with a provisioning server to receive the LUK. For example, payment cards, wearable devices such as rings and watches, and key fobs are capable of being used to conduct payment transactions as they may contain integrated circuits and short range communication capabilities (e.g., RF ID chips), but they are not capable of communicating with a remote provisioning server computer using a cellular network.

There is a need to provide for systems and methods that can allow for portable communication devices such as those that cannot receive communications over cellular networks (e.g., either permanently or temporarily) with the ability to use access tokens (e.g., payment tokens) that have previously been provisioned onto the portable communication devices.

Embodiments of the present invention provide for methods that can be performed by communication devices that may or may not have secure elements. The techniques described herein can utilize card emulation technology (e.g., Host Card Emulation (HCE), etc.) to emulate a smartcard on a communication device (e.g., a portable communication device) to allow a mobile application running on the portable communication device to conduct contactless transactions. In the card emulation environment, a mobile application can access the contactless interface (e.g., a near-field communication (NFC) transceiver) of the portable communication device via the operating system (OS) of the portable communication device without using a secure element. As compared to secure element implementations, the card emulation approach reduces the technical and commercial complexities for device issuers and/or data processors.

By removing the control of payment functionalities and account credentials from the confines of a secure element, the tamper-resistant hardware based security provided by a secure element can no longer be relied on to safeguard access data. If a secure element is not present in a communication device, access data may instead be stored in a general memory of the portable communication device. As such, the access data may be susceptible to access by malware or viruses when stored in the portable communication device.

To enhance the security of a portable communication device when conducting transactions without using a secure element, instead of using static access data stored on a portable communication device which may be valid for the lifetime of an account, the techniques described herein provision a portable communication device with encryption keys that have a limited usage or lifespan. When the lifespan of the encryption keys is exhausted, the encryption keys can no longer be used to conduct valid access transactions. In order to conduct additional access transactions using the portable communication device, new encryption keys are replenished to the portable communication device. The new limited-use encryption keys provided to the portable communication device can be renewed or replenished by a payment network via access devices such as POS terminals during the lifetime of an account. Provisioning such limited-use encryption keys via access devices is desirable, especially in the case where the portable communication devices do not have the ability to connect to remote provisioning server computers over the air via long range communication networks such as cellular networks.

In some embodiments, passive portable communication devices are already personalized and tokenized when they are made. The limited use encryption key, or LUK, in a portable communication device may be updated by an NFC interaction with an access device such as a POS terminal. The access device is able to cause the portable communication device to overwrite the existing, expired, LUK, with a new one obtained from a tokenization system. Access devices can include this LUK update functionality into their firmware. When a user taps an HCE-enabled device to conduct a transaction against an access device such as enabled POS terminal, the POS terminal would read an AID (application identifier) through regular contactless protocols, and can then check the status of the LUK residing on the portable communication device. If the LUK status indicates that the LUK is expired, the access device will cause the portable communication device to update the old LUK with a new LUK. The new LUK may then be used to create a cryptogram, which can be used in an access transaction such as a payment transaction. This “write” process that is conducted on the portable consumer device can be similar to an issuer-directed PIN-on-card update using a direct sequence of APDU (application protocol data units) commands.

Prior to discussing the details of some embodiments of the present invention, description of some terms may be helpful in understanding the various embodiments.

A “communication device” may be a device that includes one or more electronic components (e.g., an integrated chip) that can communicate with another device. A “portable communication device” be a communication device that can be transported and operated by a user. The portable communication device can be configured to transmit and receive data or communications to and from other devices. A portable communication device may be in the form of a mobile device such as a mobile phone (e.g., smart phone, cellular phone, etc.), tablets, portable media player, personal digital assistant devices (PDAs), wearable computing device (e.g., watch or ring), electronic reader device, etc., or in the form of a card (e.g., smart card) or a fob, etc. Examples of portable communication devices may also include portable computing devices (e.g., laptops, netbooks, ultrabooks, etc.).

A “server computer” may include a powerful computer or cluster of computers. For example, the server computer can be a large mainframe, a minicomputer cluster, or a group of servers functioning as a unit. In one example, the server computer may be a database server coupled to a Web server. The server computer may be coupled to a database and may include any hardware, software, other logic, or combination of the preceding for servicing the requests from one or more client computers. The server computer may comprise one or more computational apparatuses and may use any of a variety of computing structures, arrangements, and compilations for servicing the requests from one or more client computers.

An “issuer” may typically refer to a business entity (e.g., a bank) that maintains an account for a user that is associated with a portable communication device such as an account enrolled in a mobile application installed on a portable communication device. An issuer may also issue account parameters associated with the account to a portable communication device. An issuer is an example of an “authorizing entity” which may operate an authorizing entity computer. Other examples of authorizing entities may include governmental agencies, transit agencies, etc.

An “access device” may be any suitable device that can access an external system. An access device may be in any suitable form. Some examples of access devices include POS devices, cellular phones, PDAs, personal computers (PCs), tablet PCs, hand-held specialized readers, set-top boxes, electronic cash registers (ECRs), automated teller machines (ATMs), virtual cash registers (VCRs), kiosks, security systems, access systems, Websites, and the like. An access device may use any suitable contact or contactless mode of operation to send or receive data from, or associated with, a portable communication device. In some embodiments, where an access device may comprise a POS terminal, any suitable POS terminal may be used and may include a reader, a processor, and a computer-readable medium. A reader may include any suitable contact or contactless mode of operation. For example, exemplary card readers can include radio frequency (RF) antennas, optical scanners, bar code readers, or magnetic stripe readers to interact with a portable communication device.

“Short range communication” may include any suitable wireless communication between two devices that are local to each other. Typically, short range communication mechanisms can allow communications where two devices when they are within 20 meters, 10 meters, 1 meter, or 10 centimeters or 1 centimeter apart, but may not allow communication between them if they are separated by more than this. Such communication mechanisms may include NFC (near field communications), Bluetooth, Bluetooth Low Energy, Infrared, Wi-Fi, etc.

An “authorization request message” may be an electronic message that is sent to request authorization for a transaction. The authorization request message can be sent to a payment processing network and/or an issuer of a payment card. An authorization request message according to some embodiments may comply with ISO 8583, which is a standard for systems that exchange electronic transaction information associated with a payment made by a user using a payment device or payment account. The authorization request message may include information that can be used to identify an account. An authorization request message may also comprise additional data elements such as one or more of a service code, an expiration date, etc. An authorization request message may also comprise transaction information, such as any information associated with a current transaction, such as the transaction amount, merchant identifier, merchant location, etc., as well as any other information that may be utilized in determining whether to identify and/or authorize a transaction. The authorization request message may also include other information such as information that identifies the access device that generated the authorization request message, information about the location of the access device, etc.

An “authorization response message” may be an electronic message reply to an authorization request message. The authorization response message can be generated by an issuing financial institution or a payment processing network. The authorization response message may include, by way of example only, one or more of the following status indicators: Approval—transaction was approved; Decline—transaction was not approved; or Call Center—response pending more information, merchant must call the toll-free authorization phone number. The authorization response message may also include an authorization code, which may be a code that a credit card issuing bank returns in response to an authorization request message in an electronic message (either directly or through the payment processing network) to the merchant computer that indicates approval of the transaction. The code may serve as proof of authorization. As noted above, in some embodiments, a payment processing network may generate or forward the authorization response message to the merchant.

A “token” may include a substitute identifier for some information. For example, a payment token may include an identifier for a payment account that is a substitute for an account identifier, such as a primary account number (PAN). For instance, a token may include a series of alphanumeric characters that may be used as a substitute for an original account identifier. For example, a token “4900 0000 0000 0001” may be used in place of a PAN “4147 0900 0000 1234.” In some embodiments, a token may be “format preserving” and may have a numeric format that conforms to the account identifiers used in existing payment processing networks (e.g., ISO 8583 financial transaction message format). In some embodiments, a token may be used in place of a PAN to initiate, authorize, settle or resolve a payment transaction. The token may also be used to represent the original credential in other systems where the original credential would typically be provided. In some embodiments, a token value may be generated such that the recovery of the original PAN or other account identifier from the token value may not be computationally derived. Further, in some embodiments, the token format may be configured to allow the entity receiving the token to identify it as a token and recognize the entity that issued the token.

A “real account identifier” may include an original account identifier associated with a payment account. For example, a real account identifier may be a primary account number (PAN) issued by an issuer for a card account (e.g., credit card, debit card, etc.). For instance, in some embodiments, a real account identifier may include a sixteen digit numerical value such as “4147 0900 0000 1234.” The first six digits of the real account identifier (e.g., “414709”), may represent a real issuer identifier (BIN) that may identify an issuer associated with the real account identifier.

“Account parameters” may refer to information relating to an account that can be used to conduct a transaction on the account. Examples of account parameters may include information that can be used to identify an account of the user (e.g., real account identifier, alternate account identifier, token, etc.), data or information relating to the status of the account, one or more keys that are used to generate cryptographic information, data or information relating to the one or more keys, etc. An account parameter can be semi-static or dynamic. A dynamic account parameter may be an account parameter that has a limited lifespan, and which once expired, can no longer be used to conduct a transaction until the account parameter is replenished, refreshed, or renewed. A dynamic account parameter may be replenished frequently during the lifetime of an account. A semi-static account parameter may be an account parameter that has an extended lifespan that is longer than a dynamic account parameter, and can be replenished less frequently than a dynamic account parameter or not at all during the lifetime of the account.

A “key” may refer to a piece of information that is used in a cryptographic algorithm to transform input data into another representation. Examples of keys may include encryption and decryption keys. Keys may also be symmetric or asymmetric. A cryptographic algorithm can be an encryption algorithm that transforms original data into an alternate representation, or a decryption algorithm that transforms encrypted information back to the original data. Examples of cryptographic algorithms may include triple data encryption standard (TDES), data encryption standard (DES), advanced encryption standard (AES), etc.

A “cryptogram” may refer to an encrypted representation of some information. A cryptogram can be used by a recipient to determine if the generator of the cryptogram is in possession of a proper key, for example, by encrypting the underlying information with a valid key, and comparing the result to the received cryptogram.

A “limited-use threshold” may refer to a condition that limits the usage of a piece of information. A limited-use threshold may be exceeded or exhausted when the underlying condition is met. For example, a limited-use threshold may include a time-to-live that indicates an amount of time for which a piece of information is valid, and once that amount of time has elapsed, the limited-use threshold is exceeded or exhausted, and the piece of information may become invalid and may no longer be used. As another example, a limited-use threshold may include a number of times that a piece of information can be used, and once the piece of information has been used for that number of times, the limited-use threshold is exceeded or exhausted, and the piece of information may become invalid and may no longer be used.

The transaction systems according to some embodiments provides a set of functionalities to manage the deployment and usage of account parameters for transactions conducted using a portable communication device. Account parameters may include a dynamic set of data and/or a semi-dynamic set of data. The dynamic set of data may be limited-use in the sense that the dynamic set of data can be used for only a limited time or a limited number of transactions, and may need to be renewed, refreshed, updated, or replenished when the dynamic set of data has exhausted its limited usage. For example, the dynamic set of data may include a limited-use encryption key (LUK) that is used to generate a transaction cryptogram during a transaction. The LUK may be associated with a set of one or more limited-use thresholds that limits the usage of the LUK, where once the usage of the LUK has exhausted or exceeded the set of one or more limited-use thresholds, a further transaction conducted using that LUK will be declined even if the underlying account is still in good standing. The set of one or more limited-use thresholds to enforce can be determined, for example, by an issuer of the account or by a payments platform that provides the transaction service. In other embodiments, the LUK can be alternatively or additionally be used to encrypt any suitable data from the portable communication device for secure transmission to a remote server computer.

The set of one or more limited-use thresholds may include at least one of a time-to-live indicating the duration of time for which the LUK is valid, a predetermined number of transactions for which the LUK is valid, and/or a cumulative transaction amount indicating the total transaction amount summed across one or more transactions for which the LUK is valid, or any combination thereof. For example, a LUK may be valid for a time-to-live of five days, and a transaction conducted using that LUK after five days have elapsed since the LUK was generated may be declined. As another example, a LUK may be valid for a predetermined number of five transactions, and a sixth transaction (and any subsequent transaction) conducted using that LUK may be declined. As a further example, a LUK may be valid for a cumulative transaction amount of five hundred dollars, and a transaction conducted using the LUK after that LUK has already been used for transactions totaling more than five hundred dollars may be declined.

The dynamic set of data may also include a key index that is associated with the LUK. The key index may include information pertaining to the generation of the LUK. For example, the key index may be used as a seed to generate its corresponding LUK. The key index may include time information (e.g., a timestamp) indicating when the LUK is generated, and/or may include a replenishment counter value indicating the number of times that the LUK has been renewed or replenished for a particular account, mobile application, or portable communication device. In some embodiments, the replenishment counter value may indicate the number of times the LUK has been replenished within a predetermined time period, and the replenishment counter value may reset when each predetermined time period elapses. This predetermined time period may correspond, for example, to the smallest unit of time determinable from the time information, although other predetermined time periods can be used. As an example, if the time information included in the key index indicates down to which hour the current LUK is generated, the counter value may indicate the number of times the LUK has been replenished in the hour. In some embodiments, the LUK may include an application transaction counter value indicating the number of transactions that has been previously conducted by a mobile application of the portable communication device at the time the LUK is generated, or may include a pseudo random number generated by a transaction service provider or by a suitable entity such as an issuer involved in processing the transaction. It should be understood that the key index may include one or more pieces of information pertaining to the generation of the LUK, and that one or more or all pieces of information included in the key index may be used as a seed to generate the LUK.

In some embodiments, the semi-static set of data may also include limited-use account parameters that have their own set of limited-use thresholds and/or own set of use restrictions. Although in some embodiments, an account identifier such as a PAN can be used and stored on the portable communication device, a PAN may be valid for the lifetime of an account and may be used for a wide range of different types of transactions (e.g., card present transactions, online transactions, etc.). As such, to further enhance the security of the portable communication device and to reduce the impact if the account parameters are compromised, in some embodiments, instead of using and storing a PAN in the portable communication device, an alternate account identifier (e.g., an alternate PAN) or a token that is a substitute for an account identifier may be used.

An account may have one or more alternate account identifiers and/or tokens associated with the account. Each alternate account identifier or token may be restricted to the type of transactions in which the alternate account identifier or token can be used. For example, an account may be associated with a first token that can only be used for online transactions and a second token that can only be used for transactions, and an online transaction conducted using the token will be declined. Other types of use restrictions may include restrictions on what type of merchant or which merchant and/or which geographical location that the alternate account identifier or token can be used.

In the transaction system, issuers of accounts may configure service portfolio characteristics to define the risk parameters and hence the limited-use thresholds of account parameters for accounts belonging to a particular portfolio. The limited-use thresholds can be used to manage the triggers for refreshing or replenishing account parameters on a provisioned portable communication device. To ensure that the transactions are processed according to the risk parameters specified in the service profile for an account, several core functions are implemented in the system to manage the deployment and usage of the account parameters. These functions may include provisioning, active account management, verification for payment, transaction processing, lifecycle management, and post-payment processing.

FIG. 1 illustrates a transaction system 100, according to some embodiments. The core components of transaction system 100 may include a token platform 180 to manage transactions conducted using portable communication device 101. Token platform 180 may include a remote computer, and may be implemented using one or more server computers, and can be associated with or be operated by a service provider such as an issuer, payment processor, and/or other suitable entities. Token platform 180 may manage accounts, provide verification functions for transactions, manage lifecycle messages from issuer/host system 172, as well as initiate lifecycle management events.

Token platform 180 may also implement a set of key management functions that manages issuer master derivation keys (MDKs) from which the limited-use keys (LUKs) are derived. Token platform 180 may implement a set of provisioning functions that manages the preparation and delivery of account parameters (e.g., alternate account identifier or token, initial LUK and associated key index, etc.) 170 for the initial setup of the mobile application 112 on portable communication device 101. Token platform 180 may also manage the accounts for processing by issuer/host system 172, and may perform active account management functions such as functions to generate account parameters based on requests or the risk profile of the account per token platform 180 risk management parameters. Token platform 180 may also maintain the account status for each account, and manage the replenishment or refreshing of the account parameters.

In some embodiments, token platform 180 may also implement or be provided with access to a token service 182 and/or a token vault 184. Token service 182 can be implemented as a software module or as a server computer, and can be used to generate, process, and maintain tokens, which are substitute identifiers for account identifiers. During a transaction, instead of using a real account identifier (e.g., a primary account number (PAN)) to identify the account of the user, a token can be used instead to identify the account. By using a token as a substitute for an account identifier, the risk of comprising real account information can be mitigated. As indicated above, a token may have its own set of use restrictions, and token service 182 may manage the deployment and usage of the tokens according to their use restrictions. Token service 182 may be in communication with token vault 184 where the generated tokens are stored. Specifically, token vault 184 may maintain a mapping between a token and the real account identifier (e.g., PAN) represented by the token. During transaction processing, token vault 184 may be queried to retrieve the real account identifier or PAN associated with the token. In some embodiments, the token vault 184 may be implemented as a database or database server.

In transactions system 100, portable communication device 101 can be used to conduct transactions facilitated by token platform 180. The components in portable communication device 101 may include device hardware 104, a mobile operating system (OS) 114, and an applications environment 110 in which mobile application 112 may reside. Device hardware 104 may include a contactless interface 108 that can interact with a contactless reader 162 of an access device 160. Examples of contactless interface 108 may include one or more radio frequency (RF) transceivers that can send and receive communications using near-field communications (NFC), or other radio frequency or wireless communication protocols such as Bluetooth, Bluetooth low-energy (BLE), Wi-Fi, iBeacon, etc. In some embodiments, contactless interface 108 may include an optical interface (e.g., a display screen) to present payment information in the form of an image such as a quick response (QR) code, or bar code, etc. to contactless reader 162 of access device 160 when contactless reader 162 includes an optical code scanner or reader.

Applications environment 110 of portable communication device 101 may host a mobile application 112 provided by a mobile application provider. For example, if the provider of mobile application 112 is an issuer, mobile application 112 may be a mobile banking application or a separate mobile payment application. If the provider is a mobile wallet provider such as a mobile network operator or third-party wallet provider that supports multiple issuers, mobile application 112 may be a mobile wallet application.

According to some embodiments, mobile application 112 may include on-device transaction software 113 (e.g., can be in the form of a software developer kit (SDK)) integrated into mobile application 112 to support transaction functionalities. The on-device transaction software 113 may perform functions to facilitate transactions such as to take the account parameters (e.g., LUK and associated key index), generate transaction cryptograms, and deliver them to mobile operating system (OS) 114 for transmission over contactless interface 108. The on-device transaction software 113 may also manage the initial service profile parameters (e.g., limited-use thresholds) that are provided after an account has been provisioned to ensure that requests for account parameter replenishment and activities are initiated and executed.

Mobile application 112 may perform functions to manage the risk profile of the account, maintain the account status, and replenish account parameters for each account based on the on-device threshold management parameters. Mobile application 122 may also provide consumer device cardholder verification method (CDCVM) functions for transactions, and perform a set of functions that processes and responds to messages in support of post-payment processing to limit the exposure of account parameters stored on the portable communication device. For example, post-payment processing may include periodic post-payment verification of payment transactions or using post-payment information to validate account parameters replenishment requests.

In secure element based implementations, a contactless application (e.g., a mobile wallet or payment application for contactless transactions) using a contactless interface to communicate with a contactless reader of an access device would have to be coded for and be executed on a secure element in order to gain access to the contactless interface. In some embodiments, portable communication device 101 may include a mobile operating system (OS) 114 that implements a set of card emulation application programming interfaces (APIs) 116 such as host card emulation (HCE) APIs to allow mobile application 112 to gain access to contactless interface 108 without requiring the use of a secure element. For example, card emulation APIs 116 may be coded for and be executed from mobile operating system (OS) 114 of portable communication device 101, and may include programming function calls to allow mobile application 112 to receive, process, and respond to transaction communications such as Application Protocol Data Unit (ADPU) commands sent from contactless reader 162. In this manner, portable communication device 101 is able to conduct contactless transactions without requiring access to a secure element on portable communication device 101.

Once portable communication device 101 and mobile application 112 have been provisioned with the account parameters, portable communication device 101 can conduct transactions by interacting with contactless reader 162 of access device 160 (e.g., at a merchant point-of-sale (POS) location). Contactless reader 162 may include one or more RF transceivers that can send and receive communications using NFC or other radio frequency or wireless communication protocols such as Bluetooth, BLE, Wi-Fi, iBeacon, etc. In some embodiments, contactless reader 162 may include an optical code scanner or reader to conduct transactions using QR codes, bar codes, etc. Access device 160 may also include a POS acceptance device 164 and/or electronic cash register 166. Also, although a contactless reader 162 and a contactless interface 108 are illustrated in FIG. 1, it is understood that embodiments of the invention may include contact readers and contact interfaces.

To conduct a transaction, a user of portable communication device 101 may place portable communication device 101 in proximity to contactless reader 162 of access device 160, or display an image such as a QR code or bar code on a screen of portable communication device 101 for scanning by contactless reader 162 of access device 160. Portable communication device 101 may provide access device 160 with an identifier (e.g., an alternate PAN, a token, etc.) to identify the account of the user and additional information such as the limited-use account parameters or information derived from the limited-use account parameters (e.g., transaction cryptograms generated from an LUK). For example, in some embodiments, an account identifier or token, and additional information (e.g., a transaction cryptogram, account parameters, etc.) can be transmitted to access device 160 in APDU responses that are responsive to a series of APDU commands received from access device 160. Access device 160 or a merchant computer coupled to access device 160 may then generate an authorization request message including the account identifier or token, and additional information such as a transaction cryptogram and other transaction data. Access device 160 may then forward the authorization request message to a transport computer 174 of an acquirer associated with the merchant. The authorization request message can then be sent by transport computer 174 to processing network 194.

Processing network 194 may include data processing subsystems, networks, and operations used to support and deliver authorization services, exception file services, transaction scoring services, and clearing and settlement services. An exemplary payment processing network may include VisaNet™. Payment processing networks such as VisaNet™ are able to process credit card transactions, debit card transactions, and other types of commercial transactions. VisaNet™, in particular, may include a VIP system (Visa Integrated Payments system) which processes authorization requests and a Base II system which performs clearing and settlement services.

After receiving the authorization request message, processing network 194 may forward the authorization request message received from transport computer 174 to the issuer/host system 172 of the account of the user of portable communication device 101. After issuer/host system 172 receives the authorization request message, the authorization request message may be parsed, and the information in the authorization request message may be verified. For example, issuer/host system 172 may verify that the transaction cryptogram was generated by a valid LUK, and that the set of one or more limited-use thresholds associated with the LUK has not been exceeded. In some embodiments, some or all of the information in the authorization request message can also be sent to the token platform 180 for verification and processing. For example, if issuer/host system 172 does not have the capability to verify the transaction cryptogram, the processing network 194 or issuer/host system 172 may forward the transaction cryptogram to token platform 180 for verification. Alternatively, the verification of the cryptogram may have taken place before the authorization request message is received by the issuer/host system 172.

After the issuer/host system 172 decides if the transaction is authorized or not, it generates an authorization response message to indicate if the current transaction is authorized or not. The authorization response message is then sent back to processing network 194 by the issuer/host system 172. Processing network 194 then sends the authorization response message back to the transport computer 174. In some embodiments, processing network 194 may decline the transaction even if issuer/host system 172 has authorized the transaction (e.g., if a fraud risk score is too high or if limited-use account parameters are exceeded). Transport computer 174 then sends the authorization response message to the merchant computer and/or access device 160. The authorization response results, which may include transaction data for the transaction can be displayed by access device 160, or be printed out on a physical receipt.

At the end of the day, a clearing and settlement process can be conducted by processing network 194. A clearing process is a process of exchanging financial details between an acquirer and an issuer to facilitate posting to a user's payment account and reconciliation of the user's settlement position.

As illustrated above, once a portable communication device has been provided with the appropriate account parameters, the portable communication device can be used to conduct a contactless transaction, e.g., by placing portable communication device in proximity to a contactless reader of an access device. Depending upon the capabilities of the access device, a contactless transaction conducted using the techniques described herein can be processed as if the transaction is being performed with an integrated chip card (referred to as “integrated chip based transaction”), or as if the transaction is being performed with a magnetic stripe card (referred to as “magnetic stripe based transaction”). In some embodiments, the contactless transaction times using the card emulation techniques described herein may be similar to those of secure element based implementations. For example, in some embodiments, a contactless transaction using card emulation may take less than 500 milliseconds to complete.

FIG. 2 illustrates an example communication flow between a portable communication device 201 and an access device 260 during an integrated chip based transaction. In some embodiments, the communication flow may include the exchange of multiple messages between a payment device and an access device using near field communications technology for a single payment transaction. In the flow, there may be multiple messages (e.g., at least six or eight messages) that pass between the portable communication device 201 and the access device 260 in a single physical interaction (e.g., a tap) between the devices) through a wireless communication medium using a short range communication protocol or mechanism. In some embodiments, the communications can be in the form of ADPU commands and responses. However, it should be understood that other messages, messaging protocols, or formats can be used to exchange information to conduct the transaction. The communications can be carried out between a mobile application running on portable communication device 201 and a contactless reader of access device 260.

In the initiation of a transaction, the access device 260 detects the presence of portable communication device 201 in proximity to a contactless reader of access device 260. The access device 260 may send an available applications request S202 to portable communication device 201 to request information on which payment application(s) (e.g., a list of AID(s)) may be available on the mobile application of portable communication device 201. In some embodiments, the available application(s) request S202 may be in the form of a select PPSE command. The available applications request S202 may include a payment environment identifier (e.g., a PPSE name such as “2PAY.SYS.DDF01”) to identify the payment environment supported by access device 260 and the mobile application.

Upon receiving the available applications request S202, the mobile application of portable communication device 201 may identify and process the request by recognizing the payment environment identifier (e.g., PPSE name) included in the request, and respond by sending an available applications response S204 back to access device 260. The available applications response S204 may include a list of available AIDs, and may include the payment environment identifier (e.g., PPSE name) as the dedicated file name. In some embodiments, the available applications response S204 may be in the form of a select PPSE response and may include PPSE file control information (FCI). For example, the available applications response S204 may include a directory entry for each available AID. If the mobile application supports only one AID (irrespective of the number of accounts related to that AID), the mobile application may respond with a single directory entry for the supported AID. If the mobile application supports an account with multiple AIDs, the mobile application may respond with a directory entry for each of the supported AIDs. Each directory entry may include information such as the AID, an application label associated with the AID (e.g., a mnemonic associated with the AID), an application priority indicator indicating the priority of the AID, a kernel identifier indicating the application's kernel preference, and/or additional information relating to the particular AID. The available application(s) response s204 may also include other data such as FCI issuer discretionary data.

When access device 260 receives the available applications response S204, access device 204 may select a suitable application from the list of applications received in the available applications response S204 (e.g., by selecting an AID from the available AID(s) received in the available application(s) response S204). In some embodiments, the selected AID can be the highest priority AID available on the mobile application that is supported by access device 260. Access device 260 may send an application selection S206 with the selected AID to the mobile application of portable communication device 201 to continue the transaction. In some embodiments, the application selection 206 can be in the form of a select AID command.

Upon receiving the application selection S206, the mobile application of portable communication device 201 may send a terminal transaction data request S208 to request transaction data from access device 260 which may be needed to execute the transaction using the selected application/AID. In some embodiments, the terminal transaction data request S208 may be in the form of a select AID response and may include AID file control information (FCI) with the selected AID as the dedicated file name. The terminal transaction data request S208 may include a list of transaction data identifiers to request the appropriate data from access device 260, and the list of transaction data identifiers can be in the form of a processing options data object list (PDOL). The transaction data requested by the mobile application for the transaction may include terminal transaction qualifiers (TTQ), authorized amount, other amount, terminal country code, terminal verification results, transaction currency code, transaction data, transaction type, and/or an unpredictable number. The terminal transaction data request S208 may also include other data such as FCI issuer discretionary data, application program identifier, and language preference.

After receiving the terminal transaction data request S208, access device 260 may send, to the mobile application of portable communication device 201, the terminal transaction data S210 requested by the mobile application. In some embodiments, the terminal transaction data S210 may be sent in the form of a get processing options (GPO) command, and may include the requested terminal transaction data in a processing options data object list (PDOL). In some embodiments, the terminal transaction data S210 (e.g., terminal transaction qualifiers (TTQ)) may include a transaction type indicator indicating whether access device 260 supports integrated chip based transactions or magnetic stripe based transactions. Thus, in the integrated chip based transaction, access device 260 may send a transaction type indicator in the terminal transaction data S210 to indicate that access device 360 supports integrated chip based transactions. In some embodiments, the terminal transaction data S210 (e.g., terminal transaction qualifiers (TTQ)) may also include a consumer verification method (CVM) requirement indicator to indicate whether a CVM is required by access device 260 for the transaction, and also one or more CVM type indicators indicating the types of CVM supported by access device 260. Examples of CVMs that may be supported by access device 260 can include online PIN, signature, and/or consumer device CVM (CDCVM) such as a passcode used on portable communication device 201 to unlock the screen or mobile application.

Once the mobile application of portable communication device 201 receives terminal transaction data S210, the mobile application may increment its Application Transaction Counter (ATC), generate dynamic transaction processing information using at least some of the received terminal transaction data S210, and send a set of transaction processing information S212 including the generated dynamic transaction processing information to access device 260. In some embodiments, the transaction processing information S212 can be sent as a GPO response. In some embodiments, the transaction processing information S212 may include application file locators (AFLs) that can be used as file address(es) by access device 260 to read account data stored on portable communication device 201, and an application interchange profile (AIP) that can indicate the capabilities of the mobile application.

For an integrated chip based transaction, the transaction processing information S212 may include a transaction cryptogram dynamically generated using the LUK, track-2 equivalent data, and addition data such as issuer application data (IAD), form factor indicator (FFI), card transaction qualifiers (CTQ), cryptogram information data (CID), the updated ATC, and/or an application PAN sequence number (PSN). In some embodiments, the issuer application data (IAD) may include a length indicator indicating the length of the IAD, cryptogram version number (CVN) indicating the version of the transaction cryptogram, a derived key indicator (DKI) that can be used to identify a master key (e.g. a master key associated with the issuer used in generation of the LUK), card verification results (CVR), a wallet provider ID, and/or derivation data such as the key index that was used in the generation of the LUK.

The card verification results (CVR) may include information about the CVM verifying entity and the CVM verified type for the transaction. The CVM verifying entity is used to indicate which entity is performing the verification of the CVM for the transaction. The verification entity may be the access device (or terminal), a co-residing secure application, a trusted execution environment application, the mobile application itself, a remote server (e.g., the cloud), or the mobile operating system. The CVM verified type is used to indicate the CVM method used for the transaction. The CVM method may be a passcode, biometric (e.g., fingerprint), pattern lock (e.g., for a screen lock), signature, or online PIN.

If the terminal transaction data S210 received from access device 260 indicates that the CVM supported by access device 260 is a CDCVM, the CVM verifying entity and the CVM verified type can be set according to the configuration parameters of the account. For example, if the account supports CVM using a passcode that is verified by the mobile operating system of portable communication device 201, the CVM verifying entity can be set to the mobile operating system, and the CVM verified type can be set to indicate that the CVM is a passcode. In some embodiments, a CDCVM performed indicator can be included in the card transaction qualifiers (CTQ) to indicate whether the CVM verifying entity has successfully verified the user using the CDCVM indicated by the CVM verified type.

If the terminal transaction data S210 received from access device 260 indicates that a CVM is not required, the CVM verifying entity and the CVM verified type can be set to indicate that no CVM was verified.

The form factor indicator (FFI) may include information about portable communication device 201, such as a form factor indicator version number indicating the version of the form factor indicator, an indicator indicating the device type, and device feature indicators indicating what features are supported by portable communication device 201. The form factor indicator may indicate that portable communication device 201 is a standard card (e.g., ID-1 card type as specified in ISO 7811), a mini-card, a non-card form factor (e.g., key fob, watch, wristband, ring, sticker, etc.), or a mobile phone. The feature indicators may indicate whether portable communication device 201 is capable of using a passcode (can be separate from a PIN that is used during transactions), has a signature panel, has a hologram, has support for card verification values (e.g., CVV2), is capable of two-way messaging to exchange identifying information between the issuer and the user, and/or has support for using credentials (e.g., LUK, token, etc.).

After access device 260 receives the transaction processing information S212, access device 260 may send an account data request S214 to the mobile application of portable communication device 201 to read additional account data that may be stored on portable communication device 201. In some embodiments, the account data request S214 may be in the form of a read record command, and may include an application file locator (AFL) indicating the address or location of the account data that access device 260 is attempting to read. The AFL included in the account data request S214 may correspond to an AFL in the transaction processing information S212 provided from portable communication device 201.

In response to receiving the account data request S214 from access device 260, portable communication device 201 may send the account data S216 stored at the location indicated by the AFL to access device 260. In some embodiments, the account data S216 may be sent in the form of a read record response. The account data S216 may include, for example, application usage control that indicates the issuer's restrictions on the usage and services allowed for the application, the cardholder's name, customer exclusive data, issuer country code, token requester ID (e.g., if a token is used), and/or other account related data that is accessible at the AFL location.

In the process steps illustrated in FIG. 2, any of the communications (e.g., any of steps S204, S208, 2012, or S216) from the portable communication device 201 may include an indication that the current LUK (an example of a first limited use key) present on the portable communication device is expired or otherwise needs to be replenished. The portable communication device 201 can do this on its own or may do this in response to a query from the access device 260 (e.g., in steps S202, S206, S210, and/or S214). If the access device 360, the portable communication device 201, or a remote computer determines that the LUK is expired or will expire very soon, then the access device 260 may send a request for a new LUK (an example of a second limited use key) to the token platform 180 via the transport computer 174 and/or the processing network 194. The token platform 180 may then respond with a new LUK which may be sent to the access device 160, 260 via the processing network 194 and/or the transport computer 174. Once received, the access device 160, 260 may provide it to the portable communication device 101, 201 in any of the steps shown in FIG. 2 (e.g., in steps S202, S206, S210, and/or S214). The access device 160, 260 may be in short range communication (e.g., via NFC, Bluetooth or Wi-Fi) or in contact with the portable communication device 101, 201 when the new LUK is received by the portable communication device 101, 201 from the access device 160, 260. After the portable communication device 101, 201 has received the new LUK, the portable communication device 101, 201 may then write the new LUK over the prior LUK. The new LUK may then be used to generate cryptograms for subsequent transactions conducted by the portable communication device 101, 201.

In a specific illustration, in the application selection step S206 and the subsequent terminal transaction data request S208, the access device 260 may query a transaction verification log (described below) in the portable communication device 201 to determine a current status of the LUK on the portable communication device 201. In some embodiments, the access device 260 may check the value of a key index (which indicates when the current LUK was generated), a timestamp and/or a transaction counter on the portable communication device 201 and may come to a determination that the LUK is expired or about to expire. LUK expiration parameters may be stored on the access device 260 to make this determination. If the access device 260 determines that the current LUK is expired, and that a new LUK is needed, then it may send a request to a remote computer (e.g., in the processing network, token platform, or host system) for the new LUK before continuing with the actual payment transaction messaging. After the access device 260 receives the new LUK, it may provide it to the portable communication device 201, and the transaction messaging may begin where it left off, or the entire sequence of messaging may start over. If the access device 260 determines that the LUK is about to expire but can be used for the current transaction, then the access device 260 may include an indicator indicating that a LUK replacement is needed in an authorization request message to the remote computer. As will be explained below, the remote computer may then provide the new LUK in an authorization response message to the access device 260. In yet other embodiments, the access device 260 may not make any determination as to whether or not the current LUK on the portable communication device 201 is expired or is about to expire. In other embodiments, a remote computer may make this determination.

In the above-described process, the new LUK is provided during an actual payment transaction process. In other embodiments, the user may use the portable communication device to interact with an access device to obtain a new LUK for the portable communication device in a transaction that is only intended to update the LUK (and is not a payment transaction).

As noted above, for implementations using a mobile payment application in a passive wearable device, HCE still can use limited use keys to be refreshed at a time defined by the issuer—commonly a cumulative transaction amount, a number of transactions, a set amount of time—or a combination of all three. This can be achieved in a number of ways, and it is preferred that the end user experience be non-intrusive or invisible to the user. For example, in some embodiments, an issuer may configure account logic to use a fixed transaction count as an LUK guard rail. Terminal or access device firmware can be updated with additional logic to be able to identify the particular portable communication device type (e.g., wearable device type), as well as connectivity to the tokenization system and the ability to perform pre-payment actions. When the user presents the portable communication device to a terminal for payment, data such as a token cryptogram is presented to the terminal, which knows locally, for that device type, that it is about to meet or exceed its transaction or time limit, or it can pass this information to the issuer as part of an ARQC (authorization request cryptogram) payload.

In some embodiments, the access device or the POS terminal can communicate with the token service system as a trusted connection and retrieve a new LUK appropriate for that wearable and that token/PAN. The access device or POS terminal can then prompt the user with an appropriate message to tap again to complete the transaction, while updating the LUK via NFC.

In other embodiments, the access device or the POS terminal passes the token cryptogram in the clear along with other ARQC data. The issuer then approves the transaction and sends a new LUK back down to the terminal. The access device or POS terminal then displays or provides a successful transaction message to the user, but asks the user to tap their wearable or other portable communication device one additional time against the terminal to complete the updating of the portable communication device.

FIG. 3 shows a flow diagram illustrating an embodiment of the invention. In the flow in FIG. 3, a new LUK is requested through an access device prior to the transmission of an authorization request message for the transaction to a host system.

FIG. 3 shows a portable communication device 310, an access device 320, a processing network 330, and a host system 340, each in operative communication with each other. For clarity of illustration, other entities (e.g., the token platform and a transport computer) that can be in the process flow in FIG. 3 have been omitted. It is understood that such entities may optionally be present in the flow as described above with respect to FIG. 1.

In step S302, a transaction is initiated between the portable communication device 310 and the access device 320. The portable communication device 310 may be tapped against a reader in the access device 320. In some embodiments, this can start the series of messages that pass between the portable communication device 310 and the access device as shown in FIG. 2.

In step S304, the access device 320 requests data from the portable communication device 310. As mentioned above, in some embodiments, the request for data may occur in any of the messages that pass from the access device 260 to the portable communication device 201 in FIG. 2 (e.g., steps S202, S206, S210, S214). In other embodiments, the request may be a stand-alone request that is separate from the messages illustrated in FIG. 2.

In step S306, the portable communication device 310 transmits an LUK status to the access device 320. In some embodiments, the current LUK status may be passed in any of the messages from the portable communication device 310 to the access device 260 in FIG. 2 (e.g., steps S204, S208, S212, S216). In other embodiments, the request may be a stand-alone request that is separate from the messages illustrated in FIG. 2.

In step S308, the access device 320 transmits an LUK update request to the processing network 330 after the access device 320 (and/or the portable communication device 310) determines that the current LUK on the portable communication device 310 is expired or will expire soon. In some embodiments, the LUK update request may be in the form of an authorization request message such as an ISO 8583 message, but may contain no amount, zero dollars, or a nominal amount (e.g., $0.03) to indicate that it is not requesting authorization for a transaction, but is requesting a new LUK. It may alternatively including an indicator (e.g., a flag) which indicates that it is requesting an LUK and is not seeking transaction approval. The LUK update request may also include a token that corresponds to the current LUK.

After the LUK update request is received by the processing network 330, it may perform an evaluation to determine if the portable communication device 310 is authorized to receive a new LUK (e.g., by checking the current transaction data to determine if it does or does not suggest fraud, and/or verifying that the current LUK is in fact expired or about to expire). The processing network 330 may also communicate with a token platform (e.g., token platform 180 in FIG. 1) and/or an issuer/host system (e.g., host system 172 in FIG. 1) to determine if a new LUK can be issued. The processing network 330 may supply the token in the LUK update request to the token platform 180. In some cases, the real account identifier may be determined using the token.

In step S310, after the processing network 330 receives the LUK request and determines that a new LUK can be issued, the processing network 330 transmits an LUK response with the new LUK to the access device 320. The processing network 330 may also store information regarding the issuance of the new LUK for later transaction processing.

In step S312, after the access device 320 receives the LUK response, the access device 320 transmits the new LUK to the portable communication device 310. In some embodiments, the access device 320 may request that the user present the portable communication device 310 to the access device 320 to receive the new LUK. The portable communication device 310 may then store the new LUK in favor of the previously stored LUK. In some embodiments, the previously stored LUK may be deleted so that it may not be re-used.

In step S314, after the portable communication device 310 receives the new LUK, the portable communication device 310 can then be used to initiate an authorization process for the current transaction. In some instances, if the transaction being conducted is a contactless one, the access device 320 may prompt the user to place the portable communication device 310 near the access device 320 again. A series of message exchanges between the portable communication device 310 and the access device 320, such as those described above with respect to FIG. 2 may then take place. The portable communication device 310 may generate a cryptogram using the new LUK, and can transmit the cryptogram and the token corresponding to the new LUK to the access device 320. The token may be a static or semi-static token which may have been previously stored on the portable communication device 310.

In step S316, the access device 320 transmits an authorization request message with the token, the cryptogram, and a transaction amount to the processing network 330 The processing network 330 may receive the authorization request, and may then determine a real account identifier associated with the token in the authorization request message. It may do so by communicating with the previously described token platform. Once the real account identifier is received by the processing network 330, it may modify the authorization request message so that it contains the real account identifier.

The processing network 330 may also verify that the cryptogram that was generated with the new LUK that was received with the token is valid, and that the particular transaction being conducted is also consistent with the permissions provided by the cryptogram generated by the new LUK. In some embodiments, a computer in the processing network 330 may independently generate a cryptogram from an independently generated LUK (using previously stored information) or a stored copy of the current LUK that is present on the portable communication device 310, and may compare the independently generated cryptogram with the cryptogram received in the authorization request message.

In step S318, after the processing network 330 determines that the transaction being conducted is valid for the token and the cryptogram, the processing network 330 may transmit the authorization request message with the real account identifier, optionally the cryptogram or validation data associated with the cryptogram, and the transaction amount to the host system 340. The host system 340 may thereafter determine if the transaction should or should not be authorized. The host system 340 could independently verify that the transaction being conducted is consistent with the cryptogram. In such embodiments, the host system 340 may have received the information needed to verify the cryptogram from the processing network 330. The host system 340 may also perform its own transaction security checks (e.g., fraud checks) and may determine if the user has sufficient credit or funds to fund the transaction. After the host system 340 has made this determination, the host system 340 may then generate an authorization response message.

In step S320, the host system 440 may then transmit the authorization response message back to the processing network 322. The processing network 330 may retrieve the token associated with the real account identifier from the token platform, and may generate a modified authorization response message with the token.

In step S322, after the modified authorization response message is generated, the processing network 430 may transmit the modified authorization response message to the access device 420.

At the end of the day or at any other suitable time, a clearing and settlement process can take place between the processing network S430, a transport computer (not shown), and the host system 440.

FIG. 4 shows another embodiment of the invention. FIG. 4 shows the portable communication device 410 obtaining a new LUK from a processing network during an authorization process.

FIG. 4 shows a portable communication device 310, an access device 320, a processing network 330, and a host system 340, each in operative communication with each other. The process shown in FIG. 4 is efficient, as it involves a reduced number of steps compared to the embodiment in FIG. 3. For clarity of illustration, other entities (e.g., the token platform and a transport computer) that can be in the process flow in FIG. 4 have been omitted. It is understood that such entities may optionally be present in the flow as described above with respect to FIG. 1.

In step S402, a transaction is initiated by the portable communication device 410 and the access device 420. The portable communication device 310 may be tapped against a reader (or otherwise interact with the reader) in the access device 320. In some embodiments, this can start the series of messages that pass between the portable communication device 310 and the access device as shown in FIG. 2.

In step S404, the access device 420 requests data from the portable communication device 410. As mentioned above, in some embodiments, the request for data may occur in any of the messages that pass from the access device 260 to the portable communication device 201 in FIG. 2 (e.g., steps S202, S206, S210, S214). In other embodiments, the request may be a stand-alone request that is separate from the messages illustrated in FIG. 2.

In step S406, a series of message exchanges between the portable communication device 310 and the access device 320, such as those described above with respect to FIG. 2 may then take place. The portable communication device 410 may generate a cryptogram using the first LUK, and can transmit the cryptogram and the token corresponding to the new LUK, as well as the LUK status of the current LUK on the portable communication device 410 to the access device 420. The token may be a static or semi-static token which may have been previously stored on the portable communication device 410.

As noted above, in some embodiments, the access device 420 or the portable communication device 410 may have determined that the current LUK on the portable communication device 410 may expire soon or with the current transaction. The access device 420 may obtain an indicator to this effect, or may generate its own indicator and may include it in an authorization request message. The authorization request message may also include the token, the cryptogram generated using the current LUK, as well as a transaction amount. In other embodiments, neither the access device 420 nor the portable communication device determines that a new LUK is needed. In these other embodiments, a remote computer may make this determination on its own and may provide a new LUK in an authorization response message.

In step S408, the access device 420 transmits the authorization request message to the processing network 430 The processing network 430 may receive the authorization request, and may then determine a real account identifier associated with the token in the authorization request message. It may do so by communicating with the previously described token platform. Once the real account identifier is received by the processing network 430, it may modify the authorization request message so that it contains the real account identifier. The processing network 430 may also store the indicator that a new LUK is needed for the portable communication device 410.

The processing network 430 may also verify that the cryptogram that was generated with the current LUK that was received with the token is valid, and that the particular transaction being conducted is also consistent with the permissions provided by the cryptogram generated by the current LUK. In some embodiments, a computer in the processing network 330 may independently generate a cryptogram from an independently generated LUK (using previously stored information) or a stored copy of the current LUK that is present on the portable communication device 310. The computer in the processing network 330 may also compare the independently generated cryptogram with the cryptogram received in the authorization request message to verify the received cryptogram.

In step S410, the processing network 430 may transmit the authorization request message with the real account identifier, optionally the cryptogram, and the transaction amount to the host system 440. The host system 440 may thereafter determine if the transaction should or should not be authorized. The host system 440 could independently verify that the transaction being conducted is consistent with the cryptogram. The host system 440 may also perform its own transaction security checks (e.g., fraud checks) and may determine if the user has sufficient credit or funds to fund the transaction. After the host system 440 has made this determination, the host system 440 may then generate an authorization response message.

In step 412, after the host system 440 generates the authorization response message, the host system 440 may then transmit the authorization response message back to the processing network 322. The authorization response message may include the real account identifier and data indicating an approval or denial of the transaction. If the access device 420 or the portable communication device 410 determined that a new LUK was needed by the portable communication device 410, then the authorization response message may also include the indicator to generate a new LUK if the processing network 322 did not previously store it.

In step S414, after the processing network 330 receives the authorization response message, the processing network 330 may retrieve the token associated with the real account identifier, and may generate a modified authorization response message.

In step S414, the processing network 330 may also determine a new LUK and may modify the authorization response message to include the token and the new LUK. The processing network 330 may communicate with the token platform to verify that a new LUK can be issued to the portable communication device 410 and to obtain the token from the real account identifier. In some embodiments, the processing network 330 may determine that a new LUK is needed by acknowledging the indicator to provide a new LUK in the authorization request or response messages.

If the indicator to provide a new LUK was not provided in either of these messages, the processing network 330 may determine that a new LUK is needed on its own in some embodiments. For example, a computer in the processing network 330 may retrieve a key index indicating when the current LUK was generated from a data storage in the processing network 330, or from the authorization request message if it was transmitted from the portable communication device 410 to the access device 420 in step S406. It may also compare this data to other variable data such as current counters or timestamps to determine if a new LUK is to be issued. For example, if a key index indicates that the current LUK was generated at 12:00 p.m. on Jan. 1, 2017, the current transaction time and date is 11:50 a.m. on Jan. 7, 2017, and the current LUK has a lifetime of one week, then the processing network 430 may automatically determine that a new LUK can be issued, and can automatically generate the new LUK for the portable communication device 410. In another embodiment, if the key index includes a counter value of zero at the time that the current LUK is generated, the current value of a transaction counter is four (e.g., as received in an authorization request message or as retrieved from a data storage in the processing network 430), and the threshold for the issuance of a new LUK is five, then the processing network 430 may automatically determine that a new LUK can be issued, and can automatically generate the new LUK for the portable communication device 410.

In step S416, the processing network 430 may transmit the modified authorization response message including the token and the new LUK to the access device 420.

In step S418, after the access device 420 receives the authorization response message, the access device 420 may transmit the new LUK to the portable communication device 410. If the portable communication device 410 is no longer in communication with the access device 420, the access device 420 may request that the user present the portable communication device 410 to the access device 420 once more to update the portable communication device 410.

At the end of the day or at any other suitable time, a clearing and settlement process can take place between the processing network S430, a transport computer (not shown), and the host system 440.

In some embodiments, the mobile application may update a transaction verification log maintained by the mobile application at the end of a transaction to include information about the transaction in the transaction verification log. The mobile application may recognize the end of a transaction by recognizing that all transaction processing information and/or account data that may be needed by the access device to complete the transaction has been provided to the access device (e.g., recognizing that the last record defined in the AFL has been returned successfully or if no AFL, when the GPO response has been returned successfully).

FIG. 5 illustrates examples of data elements that can be included in a transaction verification log, according to some embodiments. The mobile application may maintain a transaction verification log per LUK or per set of account parameters. In some embodiments, the portable communication device may maintain a number of transaction verification logs for several LUKs or sets of account parameters, or optionally, once the current LUK or account parameters have been renewed or replenished, the transaction verification log corresponding to the previous LUK or account parameters can be deleted to save memory space. The transaction verification log information could be used by any suitable entity (e.g., an access device, processing network, or portable communication device) to determine if a new LUK can be issued.

The transaction verification log may be associated with and/or may include the key index corresponding to the LUK or set of account parameters used in the logged transactions, and a sequence counter value associated with the key index or set of account parameters indicating the number of times the LUK or set of account parameters have been replenished. For each transaction conducted using the particular LUK or particular set of account parameters, the transaction verification log may include a transaction timestamp indicating the time of the corresponding transaction, an unpredictable number (UN) provided from the access device during the transaction (if available), an application transaction counter (ATC) value associated with the corresponding transaction (e.g., a value indicating the number of transactions that has been conducted using the mobile application at the time of the transaction), and a transaction type indicator indicating whether the corresponding transaction was conducted as an integrated chip based transaction or a magnetic stripe based transaction. The transaction timestamp may be the UTC time as determined by the portable communication device at the time of the transaction.

FIG. 6 illustrates a block diagram of an example of a process 600 for generating a transaction cryptogram, according to some embodiments. Any one of the encryption functions 606, 612, and/or 618 can be the same or be different than any of the other encryption functions. For example, any one of the encryption functions may be implemented as triple data encryption standard (TDES), data encryption standard (DES), advanced encryption standard (AES), or other suitable encryption algorithms.

Process 600 can be divided into two parts—the first part relates to the LUK generation (blocks 602 to 614), which may be performed by a processing network, token platform, or host system; and the second part relates to the transaction cryptogram generation (blocks 616-620), which may be performed by a portable communication device. The first part relating to the LUK generation can be performed once to generate a LUK, and the second part relating to the transaction cryptogram generation can be performed multiple times using the LUK generated from the first part (e.g., by the mobile application) until the LUK has exceeded its set of one or more limited-use thresholds, at which time, the first part relating to the LUK generation can be performed again (e.g., by a token platform, processing network or issuer system) to replenish, renew, or refresh the LUK.

Process 600 may begin by encrypting account information 604 with a first encryption key 602 using an encryption function 606 to generate a second encryption key 608. The first encryption key 602 may be a base key that is associated with the issuer of the user's account, and the base key may be associated with a group of accounts. For example, the first encryption key 602 may be associated with a group of accounts within a range for HCE type transaction accounts. In some embodiments, the first encryption key 602 may be a master derivation key (MDK) associated with the issuer of the account associated with the account information 604, and the first encryption key 602 can be maintained at the processing network or the host system.

The account information 604 may include account identifying information such as an account identifier (e.g., a PAN), an alternate account identifier (e.g., an alternate PAN), or a token that is a substitute for an account identifier, and may additionally include user identifying information such as a sequence number (e.g., a PAN sequence number (PSN)) that identifies the particular user of the account (e.g., when multiple users use the same account). For example, the account information 604 that is used as the input to encryption function 606 can be a concatenation of the account identifying information and the user identifying information, or an inverted version of the concatenation.

In some embodiments, the second encryption key 608 being generated from the account information 604 may include multiple portions that are each generated from different variations of the account information 604. For example, the second encryption key 608 may be divided into two portions. The first portion of the second encryption key 608 may be generated by encrypting the account information 604 using the first encryption key 602. The second portion of the second encryption key 608 may be generated by inverting the account information 604 and encrypting the inverted account information using the first encryption key 602. The encryption function 606 used to generate the second encryption key 608 may be, for example, triple data encryption standard (TDES), and may use an initial chaining vector of binary zeros. In some embodiments, the second encryption key 608 generated from the account information 604 may correspond to a unique derivation key (UDK) for the account.

Process 600 may continue by encrypting key index information 610 with the second encryption key 608 using an encryption function 612 to generate the limited-use key (LUK) 614. The key index information 610 may be derived from a key index that includes information pertaining to the generation of the LUK 614, and that may be used as a seed to generate LUK 614. For example, the key index may include time information indicating when the LUK 614 is being generated. In some embodiments, the time information can be represented as the numeric string ‘YHHHH’, where ‘Y’ (0-9) represents the least significant digit of the current year, and ‘HHH’ (0001-8784) represents the number of hours since the start of January 1^(st) of the current year expressed as digits (e.g., first hour of January 1^(st)=0001). In some embodiments, the key index may also include a replenishment counter value indicating the number of times that the LUK 614 has been renewed or replenished in a predetermined time period (e.g., number of times LUK 614 has been generated in each hour). For example, the replenishment counter value can be represented as the numeric string ‘CC’ (00-99). At the beginning of each hour, ‘CC’ starts at 00 and is incremented by 1 each time LUK 614 is generated. In some embodiments, the key index may include an ATC value, or a pseudo random number generated by the processing network or the issuer.

In some embodiments, the key index information 610 that is provided as input to the encryption function 612 may be generated by padding the key index with numeric values. For example, the key index can be padded with a numeric value (e.g., 1 or 2 shown as ‘m’ or ‘n’ in FIG. 6) at the beginning of the key index and/or a numeric value (e.g., 80000000 shown as ‘xxxxxxxx’ in FIG. 6) at the end of the key index. In some embodiments, the LUK 614 being generated from the key index information 610 may include multiple portions that are each generated from different variations of the key index information 610. For example, the LUK 614 may be divided into two portions. The first portion of LUK 614 may be generated by padding the key index with a first value to generate a first padded key index (e.g., 1YHHHHCC80000000), and encrypting the first padded key index using the second encryption key 608. The second portion of LUK 614 may be generated by padding the key index with a second value to generate a second padded key index (e.g., 2YHHHHCC80000000), and encrypting the second padded key index using the second encryption key 608. The encryption function 612 used to generate the LUK 614 may be, for example, TDES or other suitable encryption algorithms, and may use an initial chaining vector of binary zeros.

After the LUK 614 is generated (e.g., by the processing network, token platform, or the host computer), the LUK 614 and the key index that includes information pertaining to the generation of LUK 614 may be provided to a portable communication device to facilitate generation of transaction cryptograms. The LUK may be associated with a set of one or more limited-use thresholds that limit the number of transactions that can be conducted using the LUK 614, such as those described herein. The data relating to the specific thresholds for an LUK may be stored remotely at a processing network, token platform, or host system.

For an integrated chip based transaction, the transaction cryptogram 620 may be generated by encrypting dynamic transaction data 616 using the LUK 614 as an encryption key in encryption function 618. The dynamic transaction data 616 may include, for example, some or all of the terminal transaction data provided from the access device to the mobile application of the portable communication device during execution of the transaction. In some embodiments, the dynamic transaction data 616 may include the following data elements: authorized amount, other amount, terminal country code, terminal verification results, transaction currency code, transaction date, transaction type, and unpredictable number; and/or may include the application interchange profile (AIP), application transaction counter (ATC), and issuer application data (IAD). In some embodiments, some data elements may be omitted, and/or additional data elements not specifically described can be included. The data set that makes up the dynamic transaction data 616 is provided as input to the encryption function 818. In some embodiments, the transaction cryptogram 620 can be generated by enciphering the dynamic transaction data 616 using a first portion of the LUK 614, deciphering the enciphered dynamic transaction data using a second portion of the LUK 614, and then re-enciphering the deciphered dynamic transaction data using the first portion of the LUK 614.

FIG. 7 illustrates a block diagram of an example of encryption function 700, according to some embodiments. In some embodiments, encryption function 700 can be used as encryption function 618. For example, the data set that makes up the dynamic transaction data 616 may be concatenated together (e.g., in the order described above), and then divided into a set of data blocks D₁ to D_(N) of equal length (e.g., 8-byte data blocks). If the dynamic transaction data 616 does not divide equally into the length of the data blocks, the missing least significant bits in the last data block D_(N) can be zero filled. The first key KA may correspond to a first portion of the LUK 614 (e.g., most significant 8 bytes), and the second key KB may correspond to a second portion of the LUK 614 (e.g., least significant 8 bytes) An iterative enciphering process may be applied to the set of data blocks D₁ to D_(N). The iterative enciphering process may include encrypting a first data block D₁ using key KA as the encryption key in a data encryption algorithm (DEA(e)). The result of the encryption is then exclusive-ORed with the next data block D₂. The result of the exclusive-OR operation is then used as the input for the next iteration of the enciphering process. The enciphering process continues until all data blocks D₁ to D_(N) has been processed, and the output I_(N) of the last exclusive-OR operation with the last data block D_(N) is encrypted to form the output of the iterative enciphering process O_(N). The output of the of the iterative enciphering process O_(N) may then be deciphered using key KB as the decryption key in data decryption algorithm (DEA(d)). The output of the deciphering process O_(N+1) is then re-enciphered using key KA as the encryption key in a data encryption algorithm (DEA(e)) to generate the output O_(N+2). According to some embodiments, the output O_(N+2) can be used as the transaction cryptogram 620.

FIG. 8 shows a block diagram of an access device 800 according to an embodiment of the invention. The access device 800 includes a processor 802. A network interface 804, an output device 806 (e.g., a display screen, speaker, etc.), a reader 810 (e.g., a contactless or contact-based device reader), an input device 812 (e.g., a keyboard, touchsreen, etc.), and a non-transitory computer readable medium 814 may be operatively coupled to the access device 800.

The non-transitory computer readable medium 814 may comprise a request generation module 814A and an LUK update determination module 814B.

The request generation module 814A may comprise code executable by the processor 802 to generate and transmit authorization request messages and/or LUK request message as described above.

The LUK update determination module 814B may comprise code, which may be executable by the processor 802 to determine if an LUK on a portable communication device is to be updated or not. In some embodiments, it may comprise code for determining based upon data in a transaction verification log, and/or the current LUK residing in the portable communication device is expired or is about to expire in the near future or in the next transactions conducted with the portable communication device.

FIG. 9 illustrates a detailed block diagram of a portable communication device 901, according to some embodiments. Portable communication device 901 may include device hardware 904 and memory 902. Device hardware 904 may include a processor 905, a communications subsystem 909, a user interface 906, a display 907 (which may be part of user interface 906), and a contactless interface 908. Processor 905 can be implemented as one or more integrated circuits (e.g., one or more single core or multicore microprocessors and/or microcontrollers), and is used to control the operation of portable communication device 901. Processor 905 can execute a variety of programs in response to program code or computer-readable code stored in memory 902, and can maintain multiple concurrently executing programs or processes. Communications subsystem 909 may include one or more RF transceivers and/or connectors that can be used by portable communication device 901 to connect with external networks (e.g., communication network 192) and communicate with other devices. User interface 906 can include any combination of input and output elements to allow a user to interact with and invoke the functionalities of portable communication device 901. In some embodiments, display 907 may be part of user interface 906.

Contactless interface 908 may include one or more RF transceivers to interact with a contactless reader of an access device. In secure element based implementations, only the secure element may have access to contactless interface 908. In the cloud-based payments techniques described herein, contactless interface 908 can be accessed by the mobile OS 914 without requiring the user of a secure element. In some embodiments, display 907 can also be part of contactless interface 908, and is used, for example, to perform transactions using QR codes, bar codes, etc.

Memory 902 can be implemented using any combination of any number of non-volatile memories (e.g., flash memory) and volatile memories (e.g., DRAM, SRAM), or any other non-transitory storage medium, or a combination thereof media. Memory 202 may store a mobile OS 914 and a mobile application environment 910 where one or more mobile applications reside including mobile application 912 (e.g., a mobile wallet application, mobile payment application, etc.) to be executed by processor 905. Mobile OS 914 may implement a set of card emulation APIs 916 that can be invoked by mobile application 912 to access contactless interface 208 to interact with an access device.

For some payments implementations, the payment system environment (e.g., PPSE) and mobile payment application functionalities are consolidated into mobile application 912, whereas secure element based implementations may provide some or all of these functionalities from a secure element. Mobile application 912 may include payments logic 950. Payments logic 950 may include contactless payment logic 958, proximity payment system environment (PPSE) logic 956, transaction verification log 954, and account parameters thresholds 952 (e.g., set of one or more limited-use thresholds associated with LUK 942). Contactless payment logic 958 may include functionalities that enable contactless communications to carried out to conduct a contactless transaction with a contactless reader of an access device. PPSE logic 956 is used to inform the access device which payment product is available on mobile application 912. The access device then uses this information to select the payment account to initiate a contactless transaction. Transaction verification log 954 can be used for post-payment support or to determine if a new LUK can be issued to the portable communication device 901. Mobile application 912 may maintain transaction verification log 954 (can be hidden from the consumer) retaining transaction details for transactions initiated from mobile application 912. Mobile application 912 may also use the transaction verification log 954 to support active account management processes and post payment interactions. Account parameters thresholds 952 (e.g., limited-user thresholds) are initially configured and can potentially be updated with different thresholds to inform mobile application 912 when to initiate a request for updated account parameters (e.g., time-to-live, number of transactions, cumulative transaction amount, etc.).

Mobile application 912 may also include account parameter storage 940 and mobile application platform (MAP) communications logic 946. Account parameter storage 940 stores the account parameters (e.g., account identifier or alternate account identifier or token, LUK 942, key index 944, etc.) that are used to initiate a payment transaction. MAP communications logic 946 is used to enable secure communications with a mobile application platform (MAP) in order to request, send, and receive information to manage a user's cloud-based payment accounts. This may include logic to consume and process information for account management logic 930.

Account management logic 930 includes logic to process information for payments services such as enrollment logic 932, provisioning logic 933, active account management logic 936, lifecycle management logic 934, and post payment interactions logic 938. Enrollment logic 932 includes logic for a consumer to initiate the enrollment of an account to the payment service. Provisioning logic 933 includes logic to process the issuer data to configure the account into mobile application 912, including the provisioning of the initial account parameters. Active account management logic 936 can be used to initiate a request with MAP to update the account parameters when account parameter thresholds have been exceeded. Lifecycle management logic 934 may include logic to initiate and process account lifecycle events such as consumer initiated delete, issuer-initiated delete, issuer-initiated suspend, and/or issuer-initiated resume, etc. Post payment interactions logic 938 is used to support payment verification. Post payment interactions logic 938 may include logic to receive and respond to requests from MAP for transaction verification log 954. Post payment interactions logic 238 can be used to support account parameters replenishment, and may include logic to extract information from transaction verification log 954 to send to MAP as part of an account parameter replenishment request.

Mobile application 912 may also include mobile application features 920. Mobile application features 920 may include consumer verification methods (CVM) logic 924, payment modes 922, and user settings 926. CVM logic 924 may include logic to confirm a mobile application passcode or on-device verification method (e.g., screen lock), or other verification information method supported by mobile application 912. Payment modes 922 may include logic to support various ways of setting up mobile application 912 and portable communication device 901 to be ready to initiate a transaction, and may include support for Manual Mode and/or Always-On Mode.

Manual Mode is a state where mobile application 912 is configured to be accessible for making a payment after the consumer has explicitly chosen to (1) open mobile application 912, (2) entered user input for a consumer verification method if required, and (3) selected an account to make a contactless payment transaction and for a single transaction or limited time. For Manual Mode, a decision can be made whether a consumer device cardholder verification method (CDCVM) will be required prior to making payment. If a CDCVM is used, then the two-tap scenario for high-value transactions may not be necessary. Conversely, to reduce barriers to use, if an issuer decides to opt for not asking for a CDCVM in Manual Mode, then the consumer will be able to conduct transactions once the conditions for Manual Mode operation are met. In this latter scenario, mobile application 912 may support entry of CDCVM if a CDCVM is requested during a high value payment.

Always-On Mode is a state where an account on portable communication device 901 (a default account) is to be continuously accessible to a contactless reader. A portable communication device with an account set in this state allows a consumer to initiate a contactless payment transaction by the presentation of the portable communication device to a contactless reader.

Although the specific examples provided above can relate to payment processing using payment tokens, it is understood that embodiments of the invention can be used in other environments that do not require payments. For example, embodiments of the invention may be used to access locations such as buildings, access data from remote servers, etc.

Embodiments of the invention have a number of advantages. For example, by allowing a limited use encryption key in a portable communication device to be updated via an access device such as a POS terminal, the portable communication device need not be in long range over-the-air communication with a remote provisioning server computer. Further, the portable communication device need not even have the ability to communicate with the remote provisioning server computer via a long range over-the-air communication mechanism. Still further, embodiments of the invention can advantageously reduce the number of communications and interactions compared to conventional provisioning processes. As noted above, in some embodiments, a limited use encryption key can be updated during a transaction authorization process. A separate provisioning message set is not required in some embodiments of the invention.

It should be understood that the present invention as described above can be implemented in the form of control logic using computer software (stored in a tangible physical medium) in a modular or integrated manner. Based on the disclosure and teachings provided herein, a person of ordinary skill in the art will know and appreciate other ways and/or methods to implement the present invention using hardware and a combination of hardware and software.

Any of the software components or functions described herein, may be implemented as software code to be executed by a processor using any suitable computer language such as, for example, Java, C++ or Perl using, e.g., conventional or object-oriented techniques. The software code may be stored as a series of instructions, or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM. Any such computer readable medium may reside on or within a single computational apparatus, and may be present on or within different computational apparatuses in a system or network.

The above description is illustrative and is not restrictive. Many variations of the invention will become apparent to those skilled in the art upon review of the disclosure. The scope of the invention should, therefore, be determined not with reference to the above description, but instead should be determined with reference to the pending claims along with their full scope or equivalents.

One or more features from any embodiment may be combined with one or more features of any other embodiment without departing from the scope of the invention.

A recitation of “a”, “an” or “the” is intended to mean “one or more” unless specifically indicated to the contrary.

All patents, patent applications, publications, and descriptions mentioned above are herein incorporated by reference in their entirety for all purposes. None is admitted to be prior art. 

What is claimed is:
 1. A method comprising: initiating communication between a portable communication device comprising a token and a first limited use key, and a point of sale terminal, which generates authorization request message for a transaction and transmits the authorization request message to a remote server; receiving, by the portable communication device, from the remote server via the point of sale terminal, a second limited use key, wherein the point of sale terminal receives an authorization response message authorizing the transaction from the remote server, the authorization response message including the second limited use key, and wherein the portable communication device receives the second limited use key from the point of sale terminal when the portable communication device is in short range communication or in contact with the point of sale terminal; and replacing, by the portable communication device, the first limited use key with the second limited use key.
 2. The method of claim 1, wherein the portable communication device is in a form of a wearable device.
 3. The method of claim 1, wherein the authorization request message comprises a transaction amount.
 4. The method of claim 1, wherein the portable communication device is a mobile phone.
 5. The method of claim 1, further comprising: encrypting, using the second limited use key and by the portable communication device, transaction data for another transaction to form a cryptogram; and transmitting, by the portable communication device, the token and the cryptogram to another point of sale terminal to conduct the transaction.
 6. The method of claim 5, wherein the transaction is a payment transaction.
 7. The method of claim 1, wherein the portable communication device does not have a secure element.
 8. The method of claim 1, wherein the second limited use key is received in a message from the point of sale terminal, the message being one of multiple messages passing between the portable communication device and the point of sale terminal in a single physical interaction between the portable communication device and the point of sale terminal.
 9. A portable communication device comprising: a processor; and a non-transitory computer readable medium, the non-transitory computer readable medium comprising code, executable by the processor to implement a method comprising: initiating communication between the portable communication device comprising a token and a first limited use key, and a point of sale terminal, which generates an authorization request message for a transaction and transmits the authorization request message to a remote server; receiving from the remote server via the point of sale terminal, a second limited use key, wherein the point of sale terminal receives an authorization response message authorizing the transaction from the remote server, the authorization response message including the second limited use key, and wherein the portable communication device receives the second limited use key from the point of sale terminal when the portable communication device is in short range communication or in contact with the point of sale terminal; and replacing the first limited use key with the second limited use key.
 10. The portable communication device of claim 9, wherein the portable communication device is in a form of a card or a wearable device.
 11. The portable communication device of claim 9, wherein the method further comprises: encrypting, using the second limited use key and by the portable communication device, transaction data for another transaction to form a cryptogram; and transmitting, by the portable communication device, the token and the cryptogram to another point of sale terminal to conduct the another transaction.
 12. The portable communication device of claim 9, wherein the portable communication device does not have a secure element.
 13. A method comprising: communicating, by an point of sale terminal, with a portable communication device comprising a token and a first limited use key; generating authorization request message for a transaction and transmitting the authorization request message to a remote server; receiving, by the point of sale terminal, a second limited use key from a remote server computer in an authorization response message authorizing the transaction from the remote server; and providing, by the point of sale terminal, to the portable communication device, the second limited use key, wherein the portable communication device is in short range communication or in contact with the point of sale terminal.
 14. The method of claim 13, wherein the point of sale terminal comprises a contactless reader, and wherein the portable communication device is capable of communicating with the contactless reader through a wireless communication medium.
 15. The method of claim 13, further comprising: receiving, by the point of sale terminal, a cryptogram and the token from the portable communication device.
 16. The method of claim 15, wherein the cryptogram is created using the first limited use key.
 17. The method of claim 15, wherein the authorization request message comprises the cryptogram and the token; and wherein the remote server is an authorizing entity computer.
 18. The method of claim 17, wherein the authorization response message comprises the token.
 19. The method of claim 15, wherein the cryptogram is generated using the second limited use key and a TDES encryption function.
 20. An access device configured to perform the method of claim
 13. 